Fix Django deprecation warnings#578
Merged
Merged
Conversation
a651b89 to
2e4e3d4
Compare
benmezger
commented
Aug 29, 2025
jelly
requested changes
Aug 30, 2025
75f82a3 to
443a778
Compare
2e560e1 to
ea7eb7a
Compare
jelly
requested changes
Sep 1, 2025
ea7eb7a to
4385817
Compare
Member
|
Thanks! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PR fixes Django deprecation warnings.
This PR does not fix all deprecation warnings, as the rest of the deprecation warnings are coming out from external libraries we use, i.e:
Ideally, once we bump Django, we would want to upgrade these modules as well.
One that made my head spin a little was the following:
Though I tried ordering the Queryset, I am not fully sure where this is coming from.